MMDF files separate into documentation, source code, mail queue, channel host name tables, programs, and logs.
Pathnames to constructed files (i.e., everything other than source code and documentation) are derived as a function of a default directory specification and the specific filename. The default directory can be overridden, for a specific file, by having the filename be a fully-specified path (starting with a slash). The default directories are defined in conf.c.
Documentation is located in the MMDF distribution tape directories doc and man. The manuals are subdivided by directories for each part of mail software, according to the V7 manual sections.
The layout and contents of the source directories are described in the document ``Installing and Operating MMDFII'' (normally in doc/administrators/* in the MMDF source directories.
The queue, for storing mail in transit, is described in queue(5).
The tables, for listing extensions to the list of local mailbox names and names of known hosts, are described in tables(5).
MMDF system logs are described in logs(5).
It is assumed that a login and uid have been assigned to MMDF. The default assumption, throughout the distribution tape, is that the login name is `mmdf'. The default location for MMDF programs is specified in cmddfldir[], for MMDF ``commands'' and in chndfldir[], for MMDF channel programs which are invoked by deliver. Both variables are specified in conf.c.
They are named to reflect their actual task Their locations are specified by the channel definitions in conf_chan.c and default to the chndfdir[] directory. It is very important that the directory containing the channel programs be accessible only by MMDF processes, or else anyone could invoke one and send unverified mail; hence make the "chans" directory have protection 0700 and be owned by MMDF. The ownership and protection modes of the channel programs depend upon the resources they consume. For example, the program which delivers mail to the local machine, ch_local, must be 04711 and owned by root, so that it can manipulate recipient's protected mailboxes. At some sites, telephone dial-out may be a protected resource, so that ch_phone should be 04711 and owned by the same user as owns the dial-out.